Looking at the code there are too many conflicts maybe because it is changed a lot in the meantime?

I was looking to https://doc.rust-lang.org/rustdoc/what-is-rustdoc.html and #237

This PR can get the maximum priority?
So we can start working on the documentation?

@Mte90 Now that the major bugs that had to be fixed by me are now gone - I will focus on this task

Can be approved? @Ph0enixKM

@Mte90 I gave myself more time to think this through if this is the format that should be generated. Have you tested it?

amber --docs test.ab

The above instruction will generate test.md file with the documentation. It works that for each file that it includes it generates appropriate file in the same directory a new markdown file. I'm still thinking if this is the best way to do it. Probably creating a separate directory docs/ with all the files would be a better approach. And also I'm thinking that this should check whether we are importing files from the same root directory or not. If we import some third party library, then this shouldn't generate documentation for it.

I want to convert it to draft since I think I have to fix the issue I described before. I've added the appropriate code to the contributing guide

I approve the idea of a dedicated docs folder, so we can see later how to implement that in the website repo.

Here is a piece of the documentation generated by the generator:

This is a documentation
That involves many interesting things

test

fun test(a: Text): Null 

This function is a test function
Here is an example:

test("Hello, World!")

foo

fun foo(a: [Num] = [1, 2, 3]): [Num] 

This also is a pretty interesting function

@Mte90 This PR is ready

@KrosFire can you actually approve this PR so that we can merge?